Allow using custom PostCSS configuration file#80
Merged
kbond merged 5 commits intoSymfonyCasts:mainfrom Jan 22, 2025
Merged
Conversation
Add tailwind cli postcss option to the build command
Test added Documentation added
Member
bocharsky-bw
left a comment
bocharsky-bw
left a comment
There was a problem hiding this comment.
To clarify, if both postcss_config_file and --postcss option are specified at the same time but with different paths, what will win? Does --postcss option override postcss_config_file?
Contributor
Author
Yes - just like the input. |
Co-Authored-By: Victor Bocharsky <bocharsky.bw@gmail.com>
bocharsky-bw
approved these changes
Jan 17, 2025
Member
bocharsky-bw
left a comment
bocharsky-bw
left a comment
There was a problem hiding this comment.
Thanks! Looks good to me
Closed
Contributor
|
Thanks @fracsi, great work! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See #79